Systems and methods of provisioning data storage and runtime configuration in telecommunications systems and devices

ABSTRACT

Systems and methods of provisioning data storage and runtime configuration in telecommunications systems and devices. The systems and methods employ at least one decentralized revision control system as a data repository for storing data, such as configuration data, and at least one data provisioning component as an interface for accessing the configuration data stored in the data repository. By employing the decentralized revision control system in conjunction with the data provisioning component, the systems and methods can provide a data storage and runtime configuration provisioning framework that is data agnostic, application agnostic, and user agnostic, while further providing at least the capability of tracking and maintaining the version history of the configuration data.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a divisional of U.S. patent application Ser. No.13/364,732 filed Feb. 2, 2012 entitled SYSTEMS AND METHODS OFPROVISIONING DATA STORAGE AND RUNTIME CONFIGURATION INTELECOMMUNICATIONS SYSTEMS AND DEVICES.

FIELD OF THE INVENTION

The present application relates generally to telecommunications systemsand devices, and more specifically to systems and methods ofprovisioning data storage and runtime configuration intelecommunications systems and devices.

BACKGROUND

Telecommunications systems and devices, such as access systems, networkmanagement systems, media switching centers, cross-connects, sessionborder controllers, etc., can be adapted via configuration data toprovide specific functionality for a target application. Based on suchconfiguration data, control software within the telecommunicationssystems and devices can control the respective systems and devices tosatisfy the requirements of the target application. For example, suchconfiguration data can be specified for a session border controller tosatisfy the requirements of access and interconnect applications withinmobile and/or fixed voice-over-Internet protocol (suchvoice-over-Internet protocol is also referred to herein as “VoIP”)networks. By adapting the session border controller using suchconfiguration data, the session border controller can be effectivelycontrolled to provide security for the interconnect and access networkinfrastructure, thereby assuring that VoIP services are madecontinuously available while maintaining a high level of systemperformance.

In typical telecommunications systems and devices, large amounts ofcomplex configuration data must generally be stored and managed.Further, within a typical target application, such configuration datagenerally has to be accessed in a controlled manner, and the history ofany changes made to the configuration data has to be tracked andmaintained. Moreover, users of such telecommunications systems anddevices generally require the capabilities of rolling back such changesto the configuration data, as required and/or as desired, andsuccessfully synchronizing the configuration data across othertelecommunications systems and/or devices over a network. However, priorattempts to provide such functionality in telecommunications systems anddevices have generally not been suited for use in real-time applicationsthat require fast, dynamic access to configuration data.

It would therefore be desirable to have improved systems and methods ofprovisioning data storage and runtime configuration intelecommunications systems and devices that better address the issuesrelating to the storage and management of data, such as configurationdata, in real-time applications.

BRIEF SUMMARY OF THE INVENTION

In accordance with the present application, improved systems and methodsof provisioning data storage and runtime configuration intelecommunications systems and devices are disclosed. The presentlydisclosed systems and methods employ at least one decentralized revisioncontrol system as a data repository for storing data, such asconfiguration data, and at least one data provisioning component as aninterface for accessing the configuration data stored in the datarepository. By employing the decentralized revision control system inconjunction with the data provisioning component, the presentlydisclosed systems and methods can beneficially provide a data storageand runtime configuration provisioning framework that is data agnostic,application agnostic, and user agnostic, while further providing atleast the capability of tracking and maintaining the version history ofthe configuration data.

In accordance with a first aspect, an exemplary system for provisioningdata storage and runtime configuration in telecommunications systems anddevices (such an exemplary system is also referred to herein as a/the“data provisioning and runtime configuration system”) includes thedecentralized revision control system, and one or more functionalcomponents including at least the data provisioning component. Forexample, the decentralized revision control system can be implementedusing the Git revision control system, or any other suitabledecentralized revision control system. The functional components canfurther include a view manager component, as well as one or morepredetermined application program components in support of thefunctionality provided by the data provisioning and runtimeconfiguration system. In accordance with a first exemplary aspect, auser can access the data provisioning and runtime configuration systemover a network via any suitable client, including, but not limited to, aweb client, which is communicably coupleable to the view managercomponent via a network connection. The view manager component can beimplemented as any suitable server interface, including, but not limitedto, a web server interface, for providing an overall view of the currentstate of the system configuration. Using the web client, the user canaccess the view manager component over the network via a web browser,which is communicably coupleable to the web server interface of the viewmanager component via the network connection. The view manager componentis communicably coupled to the data provisioning component, which, inturn, is communicably coupled to the decentralized revision controlsystem. In further accordance with the first exemplary aspect, data,such as configuration data, including but not limited to real-time data,can be stored in the data repository of the decentralized revisioncontrol system as objects (such objects are also referred to herein as“data objects”). Using the web browser, the user can communicate withthe view manager component over the network connection to request accessto, additions to, updates to, and/or deletions of specific data objectsstored in the data repository. The view manager component is operativeto communicate with the data provisioning component to implement suchaccess to, additions to, updates to, and/or deletions of such dataobjects, as requested by the user. In accordance with a second exemplaryaspect, the data provisioning component is operative to send commands,e.g., system calls, to the data repository over a source code management(SCM) interface of the decentralized revision control system, therebyimplementing the requested access to, additions to, updates to, and/ordeletions of such data objects stored in the data repository. In furtheraccordance with the second exemplary aspect, the user can communicatewith the data provisioning component to subscribe, via at least onesubscription message, to specific data objects stored in the datarepository, e.g., for the purpose of being notified whenever certaincharacteristics of such data objects change, as determined by the dataprovisioning component. In the event the data provisioning componentdetermines that such certain characteristics of the data objects have,in fact, changed, the data provisioning component can notify thesubscribing user of the change(s). In accordance with a third exemplaryaspect, one or more of the predetermined application program componentscan register, with the data provisioning component, one or moreapplication entities that may require access to the data objects storedin the data repository. The registered application entities are eachoperative to communicate with the data provisioning component to requestaccess to specific data objects stored in the data repository. Further,the data provisioning component is operative to implement such access tosuch data objects, as requested by the respective application entities.The registered application entities are each further operative tocommunicate with the data provisioning component to subscribe tospecific data objects, e.g., for the purpose of being notified whenevercertain characteristics of such data objects change, as determined bythe data provisioning component. In the event the data provisioningcomponent determines that such certain characteristics of the dataobjects have, in fact, changed, the data provisioning component notifiesthe respective application entities, as appropriate.

In accordance with a second aspect, two or more data provisioning andruntime configuration systems can be implemented as peer systems. Eachof the peer systems can include a respective decentralized revisioncontrol system, and a respective data provisioning component. Each ofthe peer systems can further include a view manager component, as wellas one or more predetermined application program components. Thedecentralized revision control systems, the data provisioningcomponents, the view manager component(s), and the predeterminedapplication program component(s) included in the respective peer systemsare each configured to operate as described above with reference to thefirst aspect of the data provisioning and runtime configuration system.The data provisioning components included in the respective peer systemsare further operative to communicate with one another over at least onemessaging interface via a first network connection. Moreover, thedecentralized revision control systems included in the respective peersystems are further operative to communicate with one another via asecond network connection, in accordance with a predetermined versioncontrol communication protocol. In the event one of the dataprovisioning components included in the respective peer systemsdetermines that certain characteristics of specific data objects storedin the data repository of the decentralized revision control systemcoupled thereto have changed, the data provisioning component can send,over the messaging interface via the first network connection, anotification of the changes to the data provisioning component includedin the other peer system. Further, the data provisioning componentsincluded in the peer systems can send commands, e.g., system calls, tothe respective decentralized revision control systems coupled thereto,thereby causing the respective decentralized revision control systems tosynchronize the changes to the data objects stored therein via thesecond network connection, in accordance with the predetermined versioncontrol communication protocol.

By employing the decentralized revision control system in conjunctionwith the data provisioning component, the data provisioning and runtimeconfiguration system can beneficially provide a data storage and runtimeconfiguration provisioning framework that is data agnostic, applicationagnostic, and user agnostic, while further providing at least thecapability of tracking and maintaining the version history of data, suchas configuration data, including but not limited to real-time data.Further, by implementing two or more such data provisioning and runtimeconfiguration systems as peer systems, any changes to the data objectsstored in the data repositories of the respective peer systems can bebeneficially synchronized using a predetermined version controlcommunication protocol, thereby assuring that none of the data are lostin the event of a failover.

Other features, functions, and aspects of the invention will be evidentfrom the Drawings and/or the Detailed Description of the Invention thatfollow.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

The invention will be more fully understood with reference to thefollowing Detailed Description of the Invention in conjunction with thedrawings of which:

FIG. 1 is a block diagram of an exemplary architecture for provisioningdata storage and runtime configuration in telecommunications systems anddevices, in accordance with an exemplary embodiment of the presentapplication; and

FIG. 2 is a flow diagram of an exemplary method of operating anexemplary data provisioning and runtime configuration system within theexemplary architecture of FIG. 1.

DETAILED DESCRIPTION OF THE INVENTION

The disclosure of U.S. patent application Ser. No. 13/364,732 filed Feb.2, 2012 entitled SYSTEMS AND METHODS OF PROVISIONING DATA STORAGE ANDRUNTIME CONFIGURATION IN TELECOMMUNICATIONS SYSTEMS AND DEVICES ishereby incorporated herein by reference in its entirety.

Systems and methods of provisioning data storage and runtimeconfiguration in telecommunications systems and devices are disclosed.The presently disclosed systems and methods employ at least onedecentralized revision control system as a data repository for storingdata, such as configuration data, and at least one data provisioningcomponent as an interface for accessing the configuration data stored inthe data repository. By employing the decentralized revision controlsystem in conjunction with the data provisioning component, thepresently disclosed systems and methods can beneficially provide a datastorage and runtime configuration provisioning framework that is dataagnostic, application agnostic, and user agnostic, while furtherproviding at least the capability of tracking and maintaining theversion history of the configuration data.

FIG. 1 depicts an illustrative embodiment of an exemplary architecture100 for provisioning data storage and runtime configuration intelecommunications systems and devices, in accordance with an exemplaryembodiment of the present application. The exemplary architecture 100includes a plurality of telecommunications systems or devices 102, 104(such telecommunications systems or devices are also referred to hereinas “telecommunications platforms”). Telecommunications platforms 102,104 can be implemented as access systems, network management systems,media switching centers, cross-connects, session border controllers, asexamples, and/or as any other suitable telecommunications systems ordevices.

In accordance with the illustrative embodiment of FIG. 1,telecommunications platform 102 includes a data provisioning and runtimeconfiguration system 101 a, and telecommunications platform 104 includesa data provisioning and runtime configuration system 101 b. Each of thedata provisioning and runtime configuration systems 101 a, 101 bincludes a decentralized revision control system, and one or morefunctional components including at least a data provisioning component.Specifically, the data provisioning and runtime configuration system 101a includes a decentralized revision control system 112 and a dataprovisioning component 116. Similarly, the data provisioning and runtimeconfiguration system 101 b includes a decentralized revision controlsystem 114 and a data provisioning component 118. With reference totelecommunications platform 104, the functional components within thedata provisioning and runtime configuration system 101 b further includea view manager component 120. Moreover, with reference totelecommunications platform 102, the functional components within thedata provisioning and runtime configuration system 101 a further includeone or more predetermined application program components 108, 110 insupport of the functionality provided by telecommunications platform102.

It is noted that the functional components within the data provisioningand runtime configuration system 101 b can further include one or morepredetermined application program components 111, 113 in support of thefunctionality provided by telecommunications platform 104.

As shown in FIG. 1, one or more user clients, such as a user client 106,can access the data provisioning and runtime configuration system 101 bwithin telecommunications platform 104 over a network. The user client106 can be implemented as a web client, as an example, or as any othersuitable client communicably coupleable to the view manager component120 via a network connection 136. Moreover, the view manager component120 can be implemented as any suitable server interface, including, butnot limited to, a web server interface, for providing an overall view ofthe current state of the system configuration. For example, the userclient 106 implemented as a web client can access the data provisioningand runtime configuration system 101 b over the network via a webbrowser communicably coupled to the web server interface of the viewmanager component 120. The view manager component 120 is communicablyconnected to the data provisioning component 118, which, in turn, iscommunicably connected to the decentralized revision control system 114.In further accordance with the illustrative embodiment of FIG. 1, data,such as configuration data, including but not limited to real-time data,can be stored in a data repository of the decentralized revision controlsystem 114 as objects (such objects are also referred to herein as “dataobjects”). For example, the decentralized revision control systems 112,114 can each be implemented using any suitable decentralized revisioncontrol system, such as the Git revision control system that provides atleast one data repository with at least history and revisioncapabilities and is not dependent on network access and/or on a centralserver.

In accordance with an exemplary mode of operation of the dataprovisioning and runtime configuration system 101 b withintelecommunications platform 104, the user client 106 communicates, usingthe web browser, with the view manager component 120 over the networkconnection 136 to request access to, and/or one or more manipulationsof, specific data objects stored in the data repository of thedecentralized revision control system 114. For example, suchmanipulations of data objects can include one or more additions to,updates to, and/or deletions of the respective data objects. Further,the user client 106 can communicate with the view manager component 120over the network connection 136 using the hypertext transfer protocol(HTTP), or any other suitable communications protocol. The view managercomponent 120 is operative to communicate with the data provisioningcomponent 118 over a connection 134 to implement such access to,additions to, updates to, and/or deletions of the specific data objectscontained in the decentralized revision control system 114, as requestedby the user client 106. Moreover, the data provisioning component 118 isoperative to send commands, e.g., system calls, to the decentralizedrevision control system 114 over an interface 132 of the decentralizedrevision control system 114, thereby implementing the requested accessto, additions to, updates to, and/or deletions of the specific dataobjects stored in the data repository of the decentralized revisioncontrol system 114. For example, the interface 132 can be implemented asa source code management (SCM) interface of the decentralized revisioncontrol system 114, or any other suitable interface. In furtheraccordance with this exemplary mode of operation of the dataprovisioning and runtime configuration system 101 b, the user client 106can communicate with the data provisioning component 118 to subscribe,via at least one subscription message, to the specific data objectsstored in the data repository of the decentralized revision controlsystem 114. For example, the user client 106 can subscribe to thespecific data objects for the purpose of being notified whenever certaincharacteristics of such data objects change, as determined by the dataprovisioning component 118. In the event the data provisioning component118 determines that such certain characteristics of the data objectshave, in fact, changed, the data provisioning component 118 generatesand sends at least one notification of the changes to the view managercomponent 120 over the connection 134, and the view manager component120, in turn, notifies the user client 106 of the changes over thenetwork connection 136, for example, via the web browser. In accordancewith an exemplary mode of operation of the data provisioning and runtimeconfiguration system 101 a within telecommunications platform 102, eachof the predetermined application program components 108, 110 canregister, with the data provisioning component 116, one or moreapplication entities that may require access to the data objects storedin the data repository of the decentralized revision control system 112.For example, the predetermined application program components 108, 110can each register one or more application entities. The applicationentities registered by the application program components 108, 110 areoperative to communicate with the data provisioning component 116 overconnections 122, 124, respectively, to request access to, additions to,updates to, and/or deletions of specific data objects stored in the datarepository of the decentralized revision control system 112. Further,the data provisioning component 116 is operative to implement suchaccess to, additions to, updates to, and/or deletions of such dataobjects, as requested, on behalf of the respective application entities.The registered application entities are each further operative tocommunicate with the data provisioning component 116 to subscribe tospecific data objects stored in the data repository of the decentralizedrevision control system 112. For example, each registered applicationentity can subscribe to the specific data objects for the purpose ofbeing notified whenever certain characteristics of such data objectschange, as determined by the data provisioning component 116. In theevent the data provisioning component 116 determines that such certaincharacteristics of the data objects have, in fact, changed, the dataprovisioning component 116 can notify the respective applicationentities over the connections 122, 124, as appropriate.

In further accordance with the illustrative embodiment of FIG. 1, thedata provisioning and runtime configuration system 101 a withintelecommunications platform 102, and the data provisioning and runtimeconfiguration system 101 b within telecommunications platform 104, canbe implemented as peer systems. In such an implementation of the dataprovisioning and runtime configuration systems 101 a, 101 b, the dataprovisioning components 116, 118 included in the respective systems 101a, 101 b are operative to communicate with one another over a messaginginterface 128. Moreover, the decentralized revision control systems 112,114 included in the respective systems 102, 104 are operative tocommunicate with one another via a network connection 130, in accordancewith a predetermined version control communication protocol, such asHTTP, UUCP, FTP, SMTP, NNTP, or any other suitable communicationsprotocol.

In accordance with an exemplary mode of operation of the dataprovisioning and runtime configuration systems 101 a, 101 b implementedas peer systems, in the event the data provisioning component 118included in the data provisioning and runtime configuration system 101 bdetermines that certain characteristics of data objects stored in thedata repository of the decentralized revision control system 114 coupledthereto have changed, the data provisioning component 118 sends, overthe messaging interface 128, a notification of the changes to the dataprovisioning component 116. Further, the data provisioning components116, 118 send commands, e.g., system calls, to the decentralizedrevision control systems 112, 114, respectively, thereby causing thedecentralized revision control systems 112, 114 to synchronize thechanges to the data objects stored therein via the network connection130, in accordance with the predetermined version control communicationprotocol. For example, each of the data repositories of the respectivedecentralized revision control systems 112, 114 may containconfiguration data. Further, the data repository of one of thedecentralized revision control systems 112, 114 may contain at least aportion of the configuration data stored in the other one of thedecentralized revision control systems 112, 114. Moreover, each of thedecentralized revision control systems 112, 114 can synchronize thechanges to the configuration data in the data objects stored therein byfetching such changes to the data objects over the network connection130, using HTTP or any other suitable communications protocol, Inaddition, the data provisioning component 116 can notify the registeredapplication entities of the changes to the data objects over theconnections 122, 124, as appropriate. By implementing the dataprovisioning and runtime configuration systems 101 a, 101 b as peersystems, a high availability deployment can be achieved that assuresthat none of the data stored in the data repositories of thedecentralized revision control systems 112, 114 are lost in the event ofa failover.

An exemplary method of operating a data provisioning and runtimeconfiguration system within the architecture 100 is described below withreference to FIG. 2, as well as FIG. 1. As depicted in step 202 (seeFIG. 2), at least one request for access to, or manipulation of, datastored in the data repository of the decentralized revision controlsystem 114 (see FIG. 1) is received at the data provisioning component118 (see FIG. 1) within telecommunications platform 104 (see FIG. 1). Asdepicted in step 204 (see FIG. 2), one or more commands are sent, by thedata provisioning component 118 (see FIG. 1), to the decentralizedrevision control system 114 (see FIG. 1) to implement the requestedaccess to, or manipulation of, the data stored in the data repository ofthe decentralized revision control system 114 (see FIG. 1). As depictedin step 206 (see FIG. 2), in the event at least a portion of the datastored in the data repository of the decentralized revision controlsystem 114 (see FIG. 1) has changed due to the requested access to, ormanipulation of, the data, a notification of the changes is sent, by thedata provisioning component 118 (see FIG. 1) over the messaginginterface 128 (see FIG. 1), to the data provisioning component 116 (seeFIG. 1) within telecommunications platform 102 (see FIG. 1). As depictedin step 208 (see FIG. 2), one or more commands are sent, by the dataprovisioning components 116, 118 (see FIG. 1), to the respectivedecentralized revision control systems 112, 114 (see FIG. 1) connectedthereto, causing the decentralized revision control systems 112, 114(see FIG. 1) to synchronize the changes to the data objects storedtherein via the network connection 130 (see FIG. 1).

It is noted that the operations depicted and/or described herein arepurely exemplary, and imply no particular order. Further, the operationscan be used in any sequence, when appropriate, and/or can be partiallyused. With the above illustrative embodiments in mind, it should beunderstood that such illustrative embodiments can employ variouscomputer-implemented operations involving data transferred or stored incomputer systems. Such operations are those requiring physicalmanipulation of physical quantities. Typically, though not necessarily,such quantities take the form of electrical, magnetic, and/or opticalsignals capable of being stored, transferred, combined, compared, and/orotherwise manipulated.

Further, any of the operations depicted and/or described herein thatform part of the illustrative embodiments are useful machine operations.The illustrative embodiments also relate to a device or an apparatus forperforming such operations. The apparatus can be specially constructedfor the required purpose, or can be a general-purpose computerselectively activated or configured by a computer program stored in thecomputer. In particular, various general-purpose machines employing oneor more processors coupled to one or more computer readable media can beused with computer programs written in accordance with the teachingsdisclosed herein, or it may be more convenient to construct a morespecialized apparatus to perform the required operations.

The presently disclosed systems and methods can also be embodied ascomputer readable code on a computer readable medium. The computerreadable medium is any data storage device that can store data, whichcan thereafter be read by a computer system. Examples of such computerreadable media include hard drives, read-only memory (ROM),random-access memory (RAM), CD-ROMs, CD-Rs, CD-RWs, magnetic tapes,and/or any other suitable optical or non-optical data storage devices.The computer readable media can also be distributed over anetwork-coupled computer system, so that the computer readable code canbe stored and/or executed in a distributed fashion.

The foregoing description has been directed to particular illustrativeembodiments of this disclosure. It will be apparent, however, that othervariations and modifications may be made to the described embodiments,with the attainment of some or all of their associated advantages.Moreover, the procedures, processes, and/or modules described herein maybe implemented in hardware, software, embodied as a computer-readablemedium having program instructions, firmware, or a combination thereof.For example, the functions described herein may be performed by aprocessor executing program instructions out of a memory or otherstorage device.

It will be appreciated by those skilled in the art that modifications toand variations of the above-described systems and methods may be madewithout departing from the inventive concepts disclosed herein.Accordingly, the disclosure should not be viewed as limited except as bythe scope and spirit of the appended claims.

What is claimed is:
 1. A system for provisioning data storage andruntime configuration in telecommunications systems or devices,comprising: a first telecommunications platform including a firstdecentralized revision control system including a first data repository,the first data repository being operative to store, as one or morereal-time data objects, at least first configuration data for a firsttelecommunications system or device, the first telecommunicationsplatform further including a first data provisioning componentcommunicably connected to the first decentralized revision controlsystem; and a second telecommunications platform including a seconddecentralized revision control system including at least one second datarepository, the second data repository being operative to store at leastsecond configuration data for at least one second telecommunicationssystem or device, the second decentralized revision control system beingcommunicably connectable to the first decentralized revision controlsystem, the second configuration data including at least a portion ofthe first configuration data, the second telecommunications platformfurther including a second data provisioning component communicablyconnected to the second decentralized revision control system, thesecond data provisioning component being communicably connectable to thefirst data provisioning component, wherein, in the event at least onecharacteristic of at least one of the one or more real-time data objectsstored in the first data repository has changed: the first dataprovisioning component is operative to generate a first notification ofthe at least one changed characteristic of the at least one of the oneor more real-time data objects, and to send the first notification tothe second data provisioning component; and having sent the firstnotification to the second data provisioning component, the first dataprovisioning component and the second data provisioning component areoperative to send one or more system calls to the first decentralizedrevision control system and the second decentralized revision controlsystem, respectively, thereby causing the first and second decentralizedrevision control systems to synchronize the at least one changedcharacteristic of the at least one of the one or more real-time dataobjects with the portion of the first configuration data stored in thesecond data repository of the second decentralized revision controlsystem.
 2. The system of claim 1 wherein the first decentralizedrevision control system and the second decentralized revision controlsystem are each implemented using the Git revision control system. 3.The system of claim 1 further comprising: a client-server interfacecommunicably connected to the first data provisioning component of thefirst telecommunications platform, the client-server interface beingcommunicably connectable to a user device, wherein the first dataprovisioning component is further operative, without being dependentupon network access: to receive at least one subscription message forsubscribing to the at least one of the one or more real-time dataobjects; to generate a second notification pertaining to the at leastone changed characteristic of the subscribed at least one of the one ormore real-time data objects; and to send the second notification to theclient-server interface for notifying a user at the user device.
 4. Thesystem of claim 1 wherein the first telecommunications platform and thesecond telecommunications platform are peer systems.
 5. A method ofprovisioning data storage and runtime configuration intelecommunications systems or devices, comprising: storing, as one ormore real-time data objects, at least first configuration data for afirst telecommunications system or device in a first data repository ofa first decentralized revision control system, the first decentralizedrevision control system being included in a first telecommunicationsplatform, the first telecommunications platform including a first dataprovisioning component; storing at least second configuration data forat least one second telecommunications system or device in at least onesecond data repository of at least one second decentralized revisioncontrol system, the second decentralized revision control system beingincluded in a second telecommunications platform, the secondtelecommunications platform including a second data provisioningcomponent, the second configuration data including at least a portion ofthe first configuration data; in the event at least one characteristicof at least one of the one or more real-time data objects stored in thefirst data repository has changed: generating, by the first dataprovisioning component, a first notification of the at least one changedcharacteristic of the at least one of the one or more real-time dataobjects; and sending, by the first data provisioning component, thefirst notification to the second data provisioning component; inresponse to the sending of the first notification to the second dataprovisioning component, sending one or more system calls by the firstdata provisioning component and the second data provisioning componentto the first decentralized revision control system and the seconddecentralized revision control system, respectively; and in response tothe sending of the one or more system calls to the first and seconddecentralized revision control systems, synchronizing, by the first andsecond decentralized revision control systems, the at least one changedcharacteristic of the at least one of the one or more real-time dataobjects with the portion of the first configuration data stored in thesecond data repository of the second decentralized revision controlsystem.
 6. The method of claim 5 further comprising: implementing eachof the first decentralized revision control system and the seconddecentralized revision control system using the Git revision controlsystem.
 7. The method of claim 5 wherein a client-server interface iscommunicably connected to the first data provisioning component includedin the first telecommunications platform, the client-server interfacebeing communicably connectable to a user device, and wherein the methodfurther comprises: in a receiving step, receiving, at the first dataprovisioning component, at least one subscription message forsubscribing to the at least one of the one or more real-time dataobjects; generating, by the first data provisioning component, a secondnotification pertaining to the at least one changed characteristic ofthe subscribed at least one of the one or more real-time data objects;and sending, by the first data provisioning component, the secondnotification to the client-user interface for notifying a user at theuser device, wherein the receiving step, the generating of the secondnotification, and the sending of the second notification are performedwithout being dependent upon network access.
 8. The method of claim 5further comprising: implementing the first telecommunications platformand the second telecommunications platform as peer systems.